Use TEE Repo Deployment Scripts#390
Merged
jjeangal merged 6 commits intocelo-integration-rebase-16.2from Apr 3, 2026
Merged
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
shenkeyao
approved these changes
Apr 3, 2026
Member
shenkeyao
left a comment
shenkeyao
left a comment
There was a problem hiding this comment.
The changes look good to me. A question about the just smoke-tests command in the "How to Test" instruction--we don't have a TEE test in the smoke test suite, right? How does this help with testing the TEE deployment?
Member
Author
You are right, it doesn't add much more to testing the functionality itself. Just that the code still compiles and works as previously. |
QuentinI
pushed a commit
that referenced
this pull request
Apr 9, 2026
* pin to different tee commit * use updated tee contract scripts * point to latest tee contract * use proxy admin from OP repo * force ref path for proxy artifact * Point to tee contracts commit at main
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR:
Removes the inline TEE contract deployment logic from this repo and delegates to the scripts in the
espresso-tee-contractssubmodule. Fixes a build-time artifact collision that was causingDeployOPChainto revert.Changes:
DeployAWSNitroVerifier.s.soldeleted: TEE contract deployment is now handled entirely byDeployTEEVerifierandDeployNitroTEEVerifierfrom the submodule.DeployEspresso.s.solsimplified: Removed duplicated proxy/verifier deployment logic. Now calls submodule scripts directly for TEE contracts; only retainsBatchAuthenticatordeployment which is OP-stack-specific.op-deployerpipeline simplified: Reduced boilerplate inopcm/espresso.goandpipeline/espresso.goaccordingly.fix-proxy-artifactupdated: The recipe already existed but only caught empty bytecode. Updated to also detect when the unversionedProxyAdmin.jsoncontains OZ v5 bytecode (non-empty but wrong source), usingast.absolutePathas the signal, then restores fromProxyAdmin.0.8.25.json.The artifact collision:
Importing
DeployTEEVerifierbrings in OZ v5'sTransparentUpgradeableProxy, which hardcodesnew ProxyAdmin(...)in its constructor. This causes Foundry to compile the OZ v5ProxyAdminand overwrite the unversionedforge-artifacts/ProxyAdmin.sol/ProxyAdmin.json.DeployImplementations.s.solcalls vm.getCode("ProxyAdmin") to build the OPCM blueprint: if it gets OZ v5 bytecode instead of OP's,DeployOPChainreverts.How to test: